home *** CD-ROM | disk | FTP | other *** search
- Subject: Re:Undo Set Property
- Sent: 8/7/96 3:50 PM
- Received: 8/7/96 4:02 PM
- From: Serge Froment, sfroment@odyssee.net
- Reply-To: ODF Interest, ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- >I've thought more about this, and examined a couple of possible designs. In
- >the end, I think the best bet is to stick with the current implementation,
- >with one minor addition. I'll explain the thinking behind not adding a
- >method first, and then I'll explain the modification that I am making.
-
- I've thought more about my part design and I am currently considering
- changing my Apple Events so my properties are independent of each other. In
- that case, the current implementation of FW_CSetPropertyCommand will suit
- my needs.
-
- The main problem I have is that some of my properties are related to each
- other. When I set them independantly, the part data as a whole may become
- invalid. What I do now is adjusting other properties so the part data is
- always valid.
-
- Is it possible to set several properties of a part with a single Apple Event?
-
- >What I am doing: I am adding a new method called
- >FW_MScriptable::SaveProperty. This method will be called by
- >FW_CSetPropertyCommand in the place of GetProperty. By default, this method
- >will just call GetProperty. I believe this should provide a solution for
- >Serge.
-
- In the case I keep my current Apple Event design, a
- FW_MScriptable::SaveProperty method can solve my problem, but then I also
- need a RestoreProperty method to be called when undoing.
-
- Serge
-
-
-